Add Access to Items
In a permission, add access to the different items that users can analyze in the solution (such as employees,
Note:
About analytic objects
Subjects include analytic objects like applicants, candidates, employees, and requisitions. When you add access to a subject, you'll also be granting access to any associated events and related objects. For example, when you add access to the Employee subject, you'll also be defining access to events such as Employee Exit and Pay Change Events as well as related objects such as Assignments and Certifications.
Events and related objects are typically items that don't have any meaning without the subject. For example, it would not make sense to have access to the Employee Exit event (terminations) without having access to the employee data for the individual who was terminated. By default, events and related objects will inherit the data security configurations from the subject.
Overlays are a collection of aggregated data that are used to support key business comparisons. Overlays include analytic objects like Engagement and Benchmarks.
About sources
Note: Limited Availability This feature is in limited availability. If you are interested, please contact your
You might configure data security to give access to data sources. Sources store data for your solution and are used to map to data load targets, such as analytic objects. When you provide access to a source, you're granting access to any data associated with the source. Let's say that you granted access to the Employee source. This means that any user assigned this permission is able to see all data ever uploaded to the Employee source.
You might choose to give access to a source to allow a user to onboard a new subject, such as uploading data, developing content for the subject in a project, and running data loads, while ensuring the user can only see underlying data for the assigned subject and not other subjects.
Users who are granted source access through permissions can:
- View all data associated with a source.
- View source configuration, but can't change the source configuration.
- View data files that they uploaded to Visier, even if the files aren't connected to the sources that the user has access to.
About managed plans
You might configure data security to give access to managed plans. Managed plans are plans created in the studio experience that allow you to configure security to limit plan visibility. When you provide access to a managed plan, you're granting access to plan items and segmentation within the plan.
Plan item security determines which plan items are visible to the user, such as Base Pay. Segmentation security determines which rows of the plan are visible based on access to the plan’s hierarchy members, such as Location. You must configure data security in order for users to view the plan. When you share a plan with users, they will only see the plan data that you have granted them access to through their permission. Plan values they do not have access to will be blank.
Add items to a permission
-
In a project, on the navigation bar, click Security > Permissions.
- Select a permission.
- In a permission, click the Data security tab and then click Add access.
- In the Select the data dialog, select the items that users with this permission can access and then click Finish.
Result: Population and data access configurations appear. To configure custom population access, see Security Filters. To configure data access, see Data Access Sets.
- Optional: Restrict access to an event or related object for a subject by hovering over the analytic object and clicking the toggle button.
Remove access to items
-
In a project, on the navigation bar, click Security > Permissions.
- Select a permission.
- In a permission, click the Data security tab.
- Hover over the item you want to remove access to and click the Remove access button .